Just trying to narrow the problem down a bit...is there any chance this has nothing to do with Android? Can you recreate the problem in a standard main() method?
I ask because if it's truly a problem in Android, then I don't mind setting up the scenario to run it in Android and see what happens. But if it's not Android-specific, it'll be a lot easier to debug and test in a main() method or JUnit test. And if you manage to recreate it outside of Android, could you share that code here so I know that I'm debugging the same thing you're trying to do?
Spring Social Project Lead