Yes we have faced this issue with CacheStream global growing out of control. We have had to create custom purge utilities to clean this data up as well as making sure any of our persistent classes that leverage a Stream class will trigger deletes on the stream when our record is deleted.

You would think the product would be able to handle this as part of cleanup of Ens.messageHeader, but alas that is not the case.