I believe json doesn't do this by default for at least a couple of
reasons
a) the solution would be programming language/version/application
specific
b) you can't differentiate strings from dates as json has no metadata
on it's fields
c) you'd have to stick to a RFC style complicated date parser to avoid
regional (=date format) problems
I actually made a patch for this myself, but it's much more cludgy
(that's why I didn't post it here), in my solution made the field look
like TIMESTAMP#TZ and added a #DATE to the key name (since I load it,
too, a hook removes this and recreates the date object transparently).