Solved! Go to Solution.
I was able to reproduce the same behavior with ArcGIS Desktop 10 SP 5. This appears to be resolved at 10.1. I would recommend following up with Tech Support so they can log this bug, attach your customer information to the bug, and offer any workarounds.