It seems that our destructor's don't get called thus preventing the proper cleanup of our code. How serious this is I don't know, but I discovered it during some memory level debugging trying to find the heart of my other problems.
Logged In: YES
That's no bug but Orbiter's default shutdown behaviour. Since this is the default behaviour on the "Extra" tab of Orbiter's launchpad, we have to live with that. You know that already, because of this you moved the "socket close" code of the telemetry to the "opcCloseRenderViewport" function in the configurator and if you have more stuff that needs to be cleaned up, you need to do it there again.