I've seen that same behaviour and I think it's a bug. I've never actually researched it so I don't know whether an explanation has ever been provided but I suspect that it's actually a Windows fault rather than a .NET fault.