Ok, I finally found out what was going on. The line number that was included with the message had no bearing on the real issue as we strip all whitespace...

Unfortunately, I think I will have to open a Microsoft incident, aaarrrgghhh.

The unfiltered query returns 16 rows, out of 3,800, before erroring out, but it tells me the offending XML...