After the server has started up and the seam application has been deployed the followin problem occures:

When requesting a .seam page the first time, a session object is created an all seam comonents are initialized.
Then something locks up the server for about 1 minute, until the page is served to the browser.
Further requests to .seam pages are delivered immediately, without this pause.

please see the seam forum, where this problem is discussed in more detail:

http://www.seamframework.org/Community/PossiblePerformanceIssueInStartingUpOrgjbossseamwebsession

Pete Muir expects this to be an Application Server problem.