Confirming this behavior in my application running under 2.0.1 FINAL. In my effort to find a work around I ended up stopping the event in my listener with mixed results. My current Ext.Container (which has the Ext.dataview.List component) includes these code fragments:
The "stopEvent()" seems to have worked around the issue described in this report under mobile Safari (iOS 5.1 in an iPhone 4S device), but did not work in the mobile browser of an arbitrary Android phone I just happened to test my app. in (Android 2.2.2 in an LG Ally device).
After testing for a while with just plain HTML, in a very simplified example of what's happening in Sencha Touch, I can confirm that this is a matter endemic to touch events. (I created a JSFiddle to demonstrate this: http://jsfiddle.net/boo1bc8y/1 ; I recommend using Chrome in Device Mode or using an actual mobile device.)
My test involves setting up a sort of "flypaper" div that listens for touchstart, touchend, and click events and that gets hidden on a touchend. It also involves an input field that also listens to these events. Upon running the fiddle, I attempt to click on the input with the flypaper over it, hopefully to prevent the touch event to give it focus. When I do, however, it turns out that after the touchend event is fired, a click event is fired a few milliseconds afterward, giving the input field focus. Testing this in Firefox in its own mobile mode results in something very similar.
Note that if the flypaper is hidden by a click event, the input does not get focus. To get around this problem, it looks like Sencha Touch will need to have its components listen to click events, not touchend.
Interesting note, as well: We also confirmed that on Apple devices and Firefox, if the user does a held touch (press the screen, hold it for a while [like, say, about a half second or longer], and then release), focus does not get passed to the input, either.