Yeah, I ran into that issue with feature geodatabases. You can get around the issue by using a mobile geodatabase, which will maintain globalid's. I just copy and pasted data into a mobile gdb before making changes. The globalid's are all the same after publishing a test service.
I'm working in a test survey, but testing the resent feature is enough of a headache I thought I would ask first.