ConversationContextDestroyedOnSessionTimeoutTest now expect session to timeout asynchronously while performing a simulated long running action on a conversation bean.

In newer WFLY versions, this is not the case. Checking on servlet specification, this shouldn't be relied upon and session should timeout if the time period between requests is bigger then x (the number you set it to be).

Therefore the test assertion that pre destroy callback and session timeout will trigger sooner then bean's business logic method is plain wrong. We need to rework the test to only verify that pre-destroy gets called in case of timeout.

See notes in this PR for more information on this test.