It doesn't really matter why it broke to be honest, something like that has to be perfect or it's useless. After it breaks for someone it's impossible to trust the system again, negating any benefits. Once bitten twice shy.
They should have done their homework on distributed systems and used something like a vector clock. MS has lots of resources and absolutely no excuse for fucking this up. Especially since small startups have made similar services that actually work.
UTC timestamps would solve the issue, unless you lied about your UTC time (hence the time change question).
I must say, unlike the first respondant to my post, while I agree it should never happen -- I think understanding why it did is interesting in of itself. But I'm just one of those people who likes understanding how people make mistakes in software.
Sometimes bubbling conflict resolution up to the user is a good idea. It's preferable to data loss.
I do wonder what would cause such an issue. You'd think that simple timestamps would catch this issue. I wonder if the original poster changed his clock to match the time for this Ignite conference and that screwed everythign up?