Got more info from Shobhit.
Some of his testcases test for behavior when an MES resource is disabled. So within those tests they would first disable an MES resource, and then re-enable it. When the next testcase runs, the MES resource is still shut down and thus the next test fails.
This is expected behavior. When an MES resource is disabled and then re-enabled, a different instance of MES is created. The application has retained the reference to the disabled (ie shut down) MES resource and needed to be restarted (such as disabled and then enabled) to reference the active and enabled MES.
Within the test case I notice a problem with the default MES. Even after an application is restarted it is still referencing the default MES that was shut down. Thus I am reopening this issue for this problem.