Our default configuration defines limit of 10K to the number of active persistent or non-persistent timers.
This jira proposes to remove this, for a few reasons:

• 10K is rather arbitrary
• The algorithm used to determine which timer entries should be evicted upon exceeding this threshold is not well suited to the timer use case, and is not currently configurable.
  • Timers most likely to be referenced soon (i.e. those with an upcoming timeout) are more likely to be selected for eviction/passivation.
• This lets us remove the file store from the default cache configuration for non-persistent timers.
  • Even when empty, a file store adds significant overhead to invocations of TimerService.getTimers() or TimerService.getAllTimers().
  • An application with a large number of EJBs that use the TimerService can quickly hit the OS open file limit