Looks like 1.6.2 fixes this. I remembered I could run jQ edge in jsFiddle and saw that the error went away when I did. With the 1.6.2 release yesterday I added it to our system build, tested and, indeed, the error is corrected.
Lesson: Don't forget to test w/ jQuery Edge in your Fiddles!
Thanks,
Jim