Please enter a Cisco TAC case if you have not already, so Cisco can track this issue and provide a fix.
This problem goes away in 5.0. This is because the OS footprint is much much smaller in 5.0 freeing up adequate space for signature config growth from sigupdates.