It seems Telerik OpenAccess have this behavior when it comes to releasing internal resources. If the connection timeout of telerik is set to 0 all resources is released when the last object scope is disposed. However, releasing the last scope and freeing internal resources sets the connection timeout to infinite (-1).
This results in a memory leak, since telerik querybuilders and caches references object scopes internally and thus prevent them from being garbage collected although they're disposed.
The current solution we have is to reset the connection timeout before creating a scope and after disposing a scope.
But this is giving us issues in long running transaction with an error "Not connected to oracle".
Does orm 2011.2 have better solution for the above problem?