Currently, a new Timer is created for each MessageManager that requires heartbeat tracking. This results in the presence of a lot of timer threads (up to one per subscription). Has a more thread-efficient solution been considered? Eg: a common ScheduledExecutorService that owns all of the message manager heartbeat tasks.