Unlock editing contexts disposed by the ERXRouteController

The ERXRouteController disposes the editing context at the end of the request handling. If the editing context is autoLocked during the request, at least one lock will remain open at disposal time (because of the coalesceAutoLocks property). This change unlocks the editing context before disposing it, avoiding inaccurate warnings when the tracing open locks option is enabled.
Merge pull request #593 from hprange/improveRestControllerCleanUp

Unlock editing contexts disposed by the ERXRouteController
Revert change caused "Should pop, but ec not found in Vector" errors in RestAPI.
- ERXApplication._endRequest() will call ERXEC.unlockAllContextsForCurrentThread() at proper time
- It's became to be possible to have unlocked ECs, not being disposed by this RouteController. It's causes unexpected side effects
Merge pull request #594 from hypeastrum/fixEcUnlockingIssue

Revert change caused "Should pop, but ec not found in Vector" errors in ...