Description of problem: unbounded-queue-thread-pool treats all threads as core threads (core-threads inherently equals max-threads) and so they don't timeout. Given this expected behavior, it may make more sense to not allow the keepalive-time parameter in this executor config and/or have the pool size configured through core-threads instead of max-threads (so it's clearer that all threads will be considered core threads). Version-Release number of selected component (if applicable): EAP 6.3.0
Closing as this is considered a feature not a bug: https://issues.jboss.org/browse/WFCORE-201