Fix for double firing touch events

Since the last update touch events (TOUCH_UP and TOUCH_DOWN at least) seemed to be firing twice for the first (primary) touch. Seems like it was creating MouseEvent to emulate a mouse event, but then not using it and instead firing the TouchEvent twice. But then these extra mouseEvents don't look like they're needed at all because the MOUSE_UP and MOUSE_DOWN events are already being triggered in the switch statement in __doProcessStageEvent. Of course, every chance that I'm missing something obvious.