At least they don’t eat SQL Server’s worker threads now, because of reduced wait times. @yogi, what resources are blocked? If they relate to Set, Hash and List tables, then it is currently by design – there’s no other deadlock-free technique, except a global lock, available to modify those tables with the current table structure.
As a part of 1.7.0 migration I’ve modified the underlying structure, so it will be possible to modify those tables without a global lock by applying a more granular locking to the concrete resources only, since all the data that belongs to the same key now reside close to each other.