subscriptions queues created in response to AMQP receiver with 'topic' capability are never cleaned up

If you subscribe to a topic over AMQP, by specifying the 'topic' capability in the link, a subscription queue is created.

If the link's source is marked durable, the subscription queue is named after the container-id and link name. If not a unique name is chosen by the broker. However it seems to me that in all cases the broker does not remove the queue when it should.

For non-durable subscriptions this should happen when the subscribing link ends, whether this is through an explicit close or whether it is implied by the client process exiting. From what I can see, in neither of these cases is the queue deleted.

For durable subscriptions, the queue should only be deleted on an explicit link close (i.e. a detach with closed set to true). This doesn't seem to happen either meaning there is no way to delete a subscription over AMQP.

The orphaned subscription queues continue to have messages published to the topic enqueued on them, meaning memory will grow and eventually may be exhausted.