[WFLY-4133] Hanging EJB threads because of a persistent timer and failed deployment

BZ 6.x https://bugzilla.redhat.com/show_bug.cgi?id=1147948
JIRA upstream: https://issues.jboss.org/browse/WFLY-4133
TimerServiceImpl gets a new state (active). This avoids getting stuck
during failed deployments when the TimerService starts before the 
EJBComponent, causing an unrecoverable lock in
BasicComponent.waitForComponentStart
Sometimes it will be a NonFunctionalTimerService if the EJB has no timeout methods.