There is no parameter or tunable that can fix this issue. Your best bet is to open an software call to RedHat asking them for an workaround or permanent solution, since CLOSE_WAIT is handled by the application.
Thanks for the feedback - I changed an EJB setting in the JBOSS config that significantly reduced the numner of CLOSE_WAIT states being created but a new release of the code resolved the issue completely.