I agree that something is up with the /PERSISTENT switch either in KiX or from outside mapping.

I was unable to have KiXtart unmap the drives that were set to be persistent.

Code:
USE "*" /DELETE /PERSISTENT
? 'ER1: ' + @ERROR
USE LIST
USE * /DELETE /PERSISTENT
? 'ER2: ' + @ERROR
USE LIST
USE "*" /DELETE
? 'ER3: ' + @ERROR
USE LIST
USE * /DELETE
? 'ER4: ' + @ERROR
USE LIST


Code:
ER1: 0
Current redirections :

No entries in list.

ER2: 0
Current redirections :

No entries in list.

ER3: 0
Current redirections :

No entries in list.

ER4: 0
Current redirections :

No entries in list.


Even thought it said there were no drives in the LIST the drives were still there and I could access the remote shares still.
 

One I removed the drive mappings and did not use the /PERSISTENT switch then KiX was able to unmap the drives.

I tested with KiX 4.23 and 2010 4.50 Release Candidate 1
both gave the same results.

At this point I have no method except to run maybe my own EnumNetworkDrives UDF and then for each one found SHELL out and have NET USE delete the connections.

Not really sure what's up, but KiX currently does not appear to be robust with the connection removal.