Increasing max-streaming-connections-per-session has slow acknowledge response?

Question

Our application is a Flex GUI with a WebLogic Server (BlaseDS) on a private network.  We were originally using IE 6, but have upgraded to IE 8.
I am trying to use publish/subscribe messaging to monitor lengthy processes on the server and received incremental data.  With 1 such process everything works fine.  But we want to allow the user to subscribe to more than 1 message destination.  So I increased the "max-streaming-connections-per-session" (default is 1) in the services-config.xml file
     <channel-definition id="process-notification-streaming-amf"
          class="mx.messaging.channels.StreamingAMFChannel">
          <endpoint url=https://{server.name}:{server.port}/{context.root}/messagebroker/streamingnotificationamf"
          class="flex.messaging.endpoints.StreamingAMFEndpoint"/>
          <properties>
               <user-agent-settings>
                    <user-agent match-on="MSIE" kickstart-bytes="2048"
                         max-streaming-connections-per-session="3" />
               </user-agent-settings>
          </properties>
     </channel-definition>
If we leave max-streaming-connections-per-session as the default value of 1 and try to subscribe to another message destination we get an error indicating limit has been reached:
     [BlaseDS]Endpoint with id 'process-notification-streaming-amf' cannot grant streaming connection to FlexClient with id '7FFC82DE-etc ' because max-streaming-connections-per-session limit of '1' has been reached.
     We upgraded to IE8 as documentation indicates IE8 allows for an increase of max-streaming-connections-per-session, where IE 6 is limited to 1.  But increasing max-streaming-connections-per-session does not quite solve the problem.  We have 3 consumers; consumer1, consumer2, consumer3.  For each of these consumers, we add event listeners for MessageAckEvent.ACKNOWLEDGE and MessageEvent.MESSAGE.
     We call consumer1.subscribe().  When we receive the acknowledge message, we call consumer2.subscribe() (likewise with consumer3)
     The problem is it takes over 2 minutes to receive the acknowledge message from the call to consumer1.subscribe().  (With max-streaming-connections-per-session set to 1, the acknowledge message is received in a few seconds.)
     So, increasing max-streaming-connections-per-session removes the error about reaching a limit, but it appears to come with a cost of a big delay in a long delay on the call to subscribe?  Or is there something we are missing?

Answer 1

I guess I will answer my own question.  Hopefully this will be useful to someone else in the future...
The problem was coming from IE being limited to 1 connection by the registry.  The solution can be found at:
http://support.microsoft.com/kb/282402
I manually performed the steps to update the registry, though microsoft provides a "Fix It"; MicrosoftFixit50098.msi
One other key element was to make sure to have kickstart-bytes="2048".