This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
The answer is definitely: no, scriptlet and directive are two well distinguished items. In a MVC vision, the scriptlet code directly interferes with the business logic of the page (it can generate new methods inside the servlet generated from the page) and that's why is is discouraged, because parameters manipulation should be controlled ONLY from your classes NOT from your page; in the page you can choose what to show and what not BUT you should not be able to change the data (oh well at least you can POST new data but this does not mean it will be changed if your business logic forbidden that operation).
On the other hand the directives handles "just" the view-side of the page (page, include, taglib): they do not manipulate your page parameters.
If you now look at the EL expressions you will see that you can compare or show some parameters but still you cannot change their inner value. Anyway if you want to have a pure MVC schema you know, I guess, that you can use the isELenabled disable also the EL and (surprise, surprise!) both script and EL can be be set per page
or per servlet (in web.xml)
but still no way to disable the directive because, again, they do not interfere with the business logic.