Persistent EJB Timers are not properly undeployed while using file persistence

While using file persistence for persistent EJB Timers, when server is restarted or timer code redeployed, new timer is added and at same time old one is restarted/keep running. In result, for example, after four restarts you got five same timers running instead of one.