Interesting.  My guess is that the issue was related to parsing XML/XHTML?  Any browser that supports HTML5 would have no issue with the named entity.  For that matter, it would handle © directly just fine as well, since we're serving up utf-8.

I can switch it to `&#169;` if you'd still prefer, although it's probably less human-readable.