Likely but that hawkee page for the JSON parser has comments, one of them talks about the cache issue and the author, suggested to use &nocache= so I'm just relaying the information.
I know the author had to change the object already to be able to support utf8 so I didn't want to suggest to use a different object because it is likely that the OP doesn't know much about COM and/or I agree, as you said, that it will require more than changing the object's name.
@Mandarb: Using socket wouldn't change anything, you would be able to send the Cache-control header, but you can send it as well with this JSON parser, look at the documentation for more information, here is an example with a dropbox url:
//jsonopen -dwu test https://dl.dropboxusercontent.com/u/4249275/json_test.txt | jsonurloption test Cache-Control no-cache | jsonget test | echo -a $json(test,test)
