The work-around appears to be to peak into the HTTP Request form items & parse it for yourself!
e.g. (in Vis. Basic)
Me.Request.Form.Item("Listbox1") will return a parsable string: "Item 03,Item 03"
I guess developers would just write a nifty little structure or class to enum thru the list... now just don't be putting commas in your data values... ;-)
So... when is a .selected not a .selected? When Microsoft wants to de-duplicate selected values, without warning us!
Perchance there's some kind of global setting to prevent this kind of fuzzy UI object behavior?