Hmm... you could just turn off 'use mouse input', but then I guess that's inconvenient for desktop. I've made it turn that option off on mobile in the next build (using the runtime isMobile property since that better detects mobile platforms).
Edit: actually, this might not work since you can actually add mouse devices to Android or other touch-screen systems, and the mouse will be broken if you use this code. So it doesn't fix it, it only breaks it under different circumstances.
We try to prevent the default behavior on all touches, which ought to prevent Android firing a mouse event afterwards, so I think this is actually an Android bug. Which version of Android and which browser are you testing on? It shouldn't happen with Chrome for Android.