Here's the code that causes it:
<script type="text/javascript" src="/__utm.js"></script>
<noscript>
<meta http-equiv="refresh" content="0; url=http://www.mainetoday.com/membercenter/nojscookie.html">
</noscript>
The HTML noscript element uses your browser's identification to decide what to do with you. If your browser doesn't support scripts, the noscript element can pass scripted information to you. It's designed to offer alternative content to a user with a pre-JavaScript browser, and the W3C would probably birth kittens if they saw it being used to shut you out of a webpage. This is probably enough of a dick move to warrant writing an email to the site's webmaster or using a blog to warn others off the site.
I guess if you want your script blocker to work, it has to identify itself differently. It would have to identify your browser as supporting scripts, and just not run them. So of all the script blockers out there, some might work, and some might not, depending on how they are programmed.