I agree with you, but in case of debugging, have the really used charset could be interesting, especially with in reason of this pull request.

This wouldn't cause any problem and would help.

Moreover, JSON can be encoded with UTF16 and 32, so ...

http://www.ietf.org/rfc/rfc4627.txt (3rd section)