In the implementation of the DatabaseManager, when retrieving the environment the deleteLockingProcessAndGetEnvironment is called to forcibly "get" the environment, which is not the proper way to acquire the database.
A possible solution is to just remove it, or test for edge cases where remnant locks need to be removed when the process that holds the lock was not able to do the proper cleanup.