Because the async resource cleanup doesn't check whether the channel it's attempting to send the delete commands over is currently valid, it means that it will keep attempting to delete the directory over and over.  This will cause the GC to hold onto the Channel/machine resources.

In installations that use the Jenkins cloud feature, nodes that were deleted shortly/immediately after a job being finished will slowly leak resources till they OOM.