Based on the comment that the app was installed in a fresh computer then it does not seem likely that the cache is a problem. Though it is quite strange. As the documentation (http://symfony.com/doc/current/reference/configuration/framework.html#http-method-override) shows, this parameter was added to 2.3.
If you look in: Symfony\Bundle\FrameworkBundle\FrameworkBundle we see that that parameter is being checked in the bundle boot method.
From: Symfony\Bundle\FrameworkBundle\DependencyInjection\FrameworkExtension we see that the parameter is being added to the container with a default value of true during the build process.
So it appears that boot is being called before the build process. Consider add some die() statements to the framework code just to confirm that this indeed happening.
Then I would suggest that you try going in your AppKernel and commenting out the inclusion of all the non-standard bundles. It sort of seems that one of them might be messing around with the boot process? Sounds unlikely but maybe. Just use app/console to startup your app. Stay in debug mode.
The other option would be to start with a working standard application and then add your bundles in until the problem reappears.
BTW, what version are you upgrading from and are you using composer?