It would appear that the Execute method on a the ADO Connection object leaks memory when a CREATE TABLE or SELECT INTO statement is executed (maybe others, DROP TABLE is OK) from javascript, even when specifying adExecuteNoRecords. The only work around I can find is to close the connection and re-open.