SmartClient Server alters dateTime fields in records serving session of IE9

Our organization uses custom datasource constructor on the tomcat server with a cache of records in memory stored as hashmaps. Some of the fields are dateTime entries with timeZone information. For performance reasons, upon request from a browser, we send back scoped results directly by reference. All browser types receive the correct information except IE (only tested with 9), which has dateTime adjusted by hours exactly the opposite of the timeZone stored on webserver. What is worse and not acceptable is that data on the webserver is also modified permanently as if "corrupted"(10am EST will become 3pm EST). This is feasible because we return by reference to the cache itself and over the time of polling for updates from the listgrid, the field value will either move into the future or past indefinitely. To us, this is a serious show-stopper and after investigation we determined the data alternation happened after DSResponse was passed back from fetchData() and thus entirely in SmartClient Server's hand. Since we don't have exposure to the server side code I cannot provide code samples.
The version we use is v8.3p_2013-05-07/Pro Deployment (built 2013-05-07) and we do have purchased basic support.