Memory leak possible in KahaDB when MQTT clients connect and lookup previous durable topic subscriptions

When an MQTT client connects using the default subscription strategy it does a lookup in the persistence adapter to find previously registered durable topic subscription so that they can be recovered.

There is an issue where the lookup causes an entry to be placed into a set to track an async tasks data structure and never removed thereafter which leads to a build up over time in the tracking set.