As BC says, I can't see that it would, especially as the option will still be there in about:config. Noscript does many things that Firefox does not allow by default, so I doubt this will affect Noscript.
For me, the issue is sort of the same as one of the commenters. In order to disable Javascript, you will have to use about:config, which requires acknowledging that it's dangerous, and that you know what you are doing, etc. But disabling javascript isn't dangerous at all; in fact, running javascript all the time could be considered more dangerous, and it why we have add-ons like noscript.
It just seems like the option should be part of the application itself, rather than hidden away. (it removes the Options->Content "Enable Javascript" checkbox entirely, making it impossible to disable without advanced techniques or addons, and I find it hard to really see where they are coming from with this sort of change.
