It's not you, this is a jQuery bug with IE filed in the error tracker here , here and here .... unfortunately, it looks like it will be jQuery 1.5 before they make changes fixing it.
Currently (only in IE), the DOM 0 event handler (your built-in) is launched onchange, and then the jQuery handler ... something about this execution forces the DOM 0 handler to start again.