Shared classpaths and jars manager for jobs in sql gateway cause confliction

Current all jobs in the same session of sql gateway will share the resource manager which provide the classpath for jobs. After a job is performed, it's classpath and jars will be in the shared resource manager which are used by the next jobs. It may cause too many unnecessary jars in a job or even cause confliction