Issue 113679

The code in disposeEnvironment() does the following:

If pContext->m_pBridgeImpl->m_bDisposed is FALSE, it calls
pEnvRemote->dispose(...) and pEnvRemote->release()

However, the access to m_bDisposed is not guarded by a mutex. So, even if the
bridge has already started to dispose (RemoteEnvironment_thisDispose() has set
m_bDisposed to TRUE, but m_bDisposed in this thread is still seen as FALSE by
the CPU), the code will walk into the if branch.

On the other hand, if the bridge has already been disposed,
pEnvRemote->release() will never be called.

Wouldn't it be more correct to completely remove the check for m_bDisposed, and
just walk into the if-branch every time?

After doing this change, I also found out that I need to clear the mutex in
RemoteEnvironment_thisDispose() directly after setting the m_bDisposed flag.
Otherwise the OReader thread might deadlock waiting on the mutex, while the
thisDispose() method waits for the thread to finish.