Camel pooled threads never die when defined in SwitchYard

Deploy the enclosed sample application, change the file binding to something friendly for your machine. Take a thread dump right after application deployment. Grep it for the thread name (i.e. jstack $PID | grep I048) Note the threads. See the name 'I048' assigned in the RouteBuilder. Drop a few files, see the thread count go up. Note the 'KeepAliveTime' param set on the profile. Set this to whatever you'd like, it seems not to change anything. Undeploy the SwitchYard app. Continue monitoring with jstack, the custom threads keep on waiting on condition.