Potential problem in 4.3.3RC3

I mentioned the following issue when 4.3.3RC1 was released. Perhaps the general feeling is that it is a non-issue, but I think it might at least cause a lot of support traffic on the lists. When I tested SquirrelMail on my test server (reporting set to E_ALL) I get a load of 'headers can't be sent' messages. The reason is that on 4.3.2 and it's predecessors, it was ok to make multiple calls to session_start(). However, from 4.3.3RC1 onwards, every call after the first one generates a warning message. So on production machines with appropriate error_reporting levels, nobody is going to notice, but on E_ALL machines all hell breaks loose because headers then can't be sent. I suspect this will affect many more applications than just SquirrelMail. I apreciate that issuing the warning is proably the technically correct thing to do, but given that there don't seem to be many practical advantages in issuing the warning, should we revert to the old behaviour? Cheers -- Phil Driscoll