Yep I have this exact same problem, while I'm not sure it is a "bug" per se, I think it might have been intended to be a design to help with the newer UI aspects of Windows 8, I do believe the programing logic on how and when it happens is broken.
Like others have found out, it's definitely related to having Metro apps "opened", but I know that I've had times when I force closed all Metro apps and it remains, as well as I've had a few times with Metro apps being open and the mouse catching didn't happen.
The most consistent way to reproduce is to open a Metro app; if that isn't enough, try switching/minimizing between the desktop and that app(s).
The two biggest problems I have with it are: 1) it's inconsistent on when it activates; if due to having a Metro app opened/close/minimized etc., and 2) there seems no way to turn it off.
I actually believe this function might be useful... if it correctly understood when a Metro app was actually open and more importantly in *focus*. If it was designed solely to help with activating the charms bar or metro app switcher, even when Metro apps are not open, I would greatly desire the ability to disable it when I'm strictly on the desktop or even when metro apps are technically "open" but are minimized.
Regardless of its intended purpose and the fact that the programing logic is inconsistent/broken, there needs to be an option, a simple check box, to turn it off and return it to how 8.0/8.1 pre-update worked.
I assume there's a registry edit we can make to turn it off, but if there truly is no setting/check box a normal user can access to turn it off, then I am highly disappointed in the WinDiv team who implemented this without considering such things.
For an update that's supposedly meant to help desktop users enjoy Windows 8 more and even maybe encourage them to adventure further into Metro apps, this change (while seemingly intent on being helpful) adds a great deal of annoyance and making simple multi monitor tasks infuriating.
If this somehow is just a weird bug that no one actually designed, where the mouse pauses at the edge of a monitor and only breaks through at a certain speed threshold... then that really is an impressive bug and hopefully a fix will be out soon.
If not, and this is just a "feature" with inconsistent activation... then please fix that activation logic and.... even better yet, give us the option to turn it off.