Is it really myopic to expect the OS to get out of the way when the user specifically requests it? Again, I completely grasp the need for signing. It's nice that apps that only need very limited capabilities can continue to go unsigned.
What you still haven't communicated to me is where the problem comes in with a developer having access to all APIs through the free program, given that the signing is only valid for the one IMEI. If it were valid for more, I'd get it, but you're already allowing access to a lot of sensitive APIs, so why not the manufacturer capabilities (and AllFiles?).
Security should be balanced with ease of use and letting the user do what they want, should they really really want that and indicate that they know what they're doing. (I'd say figuring out how to use Symbian Signed is plenty of a barrier to entry) Pre Symbian 9 was too lax, hence the viruses and other badness that was capable of going on. WM is also too lax. Symbian 9 has gone too far in the other direction. It was worse back before the Express program allowed no cost signing for development on one device or personal use.
I'm not a rabid freak, but rather than explaining your position, you've treated me as one, apparently because you think that every person who writes software writes it for sale or distribution. I write it for myself, and on rare occasion for my employers. Sadly, the Symbian Signed program seems to be exclusively targeted towards people who develop for sale or distribution to third parties.
P.S. I shouldn't be forced to use Java to develop for my own phone. I should be able to use any language I choose and get the capabilities I need on my single IMEI. (lately, I've been enjoying Python)
P.P.S. I should have been more clear with this "I shouldn't have to pay thousands of dollars to install an internally developed app on phones my company owns." You are correct that there was some exaggeration on my part regarding the cost, although it wouldn't be an exaggeration if the internally developed app for deployment solely on the enterprise's phones came up for review and failed, thus requiring the company to pay testing fees for any future revisions of the app. (or at least the next two)