AMQ 6 implemented the capability to assign a timeout for offline durable subscribers via property offlineDurableSubscriberTimeout.

AMQ 7 does allow for removal of addresses and expiration of messages for offline subscribers, but the subscribers remain, occupying broker heap space.

In our use case we have 1000s of MQTT subscribers that must be subscribed with clean=false to prevent dropping of messages when clients traverse network boundaries, but these clients subscribe with new subscriptions when restarted, leaving old subscriptions occupying heap space until the broker is restarted.

This functionality would allow for expiration / cleanup of Durable subscriptions / persistent MQTT subscriptions after a configurable timeout, eliminating the need for clean restarts each day.