Thanks for pointing this out. This was caused by the change in jQuery that allows .remove() to be called while keeping data associated with the elements. I've fixed the way we proxy .remove() for the widget factory so that it will work with jQuery 1.4. We do have a plan going forward to remove the proxying to avoid unexpected problems like this. Here's the ticket: