I agree 
But in my case the subscription would be cleaned up as the current process is allready monitored by PubSub when using PubSub.subscribe, in the case of termination.
The main reason for my suggested feature is that the parent process is not terminated when you make a change in the page that removes the component.
The LiveView process is still very much alive even though the component is not present anymore.
Since the subscription happens in the LiveComponent mount function and I forward the PubSub messages using send_update to the component, when the component is removed my code would still try to send_update to a component that is now not present anymore
I offcourse handle this as described earlier but would be nice to have this as a feature that was part of the Component instead
