Cancelled timer not removed from internal cache when using persistent timers

1.) 2 WildFly server with the same configuration using an EJB timer with DB persistence. 2.) the attached application ( playground-jar.jar ) that starts 2 timer (1 scanner timer and 1 future timer) the scanner timer runs every couple of seconds (e. g. 4 sec) the future timer will never execute, it is always only cancelled and newly created by the scanner timer (always adding 1 hour) 3.) running both servers with simple standalone.xml with persistent database timer with a refresh-interval of 2000 (2 seconds) configuration and a port offset It can be observed that the output for getTimers() on one node will increase in it's number.