i think there is a serious problem with your conversation management...

ill give you a bit of constructive code to add to your project and watch your conversations

package com.denniscg.action;

import javax.ejb.Stateless;

import org.jboss.seam.annotations.In;
import org.jboss.seam.annotations.Logger;
import org.jboss.seam.annotations.Name;
import org.jboss.seam.annotations.Observer;
import org.jboss.seam.contexts.Context;
import org.jboss.seam.core.Conversation;
import org.jboss.seam.log.Log;

@Stateless
@Name("conversationListener")
public class ConversationListenerBean implements ConversationListener {

     @Logger
     private Log log;

     
     @Observer(value="org.jboss.seam.endConversation")
     public void observeConversationEnd() {
          log.info("CONVERSATION Ended");
          
     }

     @Observer(value="org.jboss.seam.beginConversation")
     public void observeConversationStart() {
          log.info("CONVERSATION Started");
          
          

     }

     
}

package com.denniscg.action;

public interface ConversationListener {

     void observeConversationStart();
     void observeConversationEnd();
}

need to keep track of your conversations. and depending on what you are doing, end one before starting another. cant just create a bunch of transaction without managing them correctly or you are going to see serious lag on your server. unless told to retain the parent conversation,, each ajax command gets its own. figured this out when working with Seam Remoting. i think there is a couple pages written about it on this forum a few years ago.