Good catch, but I am wondering the best way to handle this... I personally get these errors in my logs and it reminds me to scrub the incoming data better prior to sending. This would mask the real issue, no?

Thoughts @visionmedia?