This was discovered while working on RT-34136.
The problem was that we save the current pendingTouchPoint events for the next processing cycle, but when multi-touch is disabled we:
1) save more points then required (n instead of 1)
2) in some cases where the logic decide that a point is release or still we copy the information from the pending event which is wrong/inaccurate

Need to make sure that only the 'usable' and 'active' points are saved.