Perhaps not. But it's too late to loose the safety after one has already been out drawn.

In any case, removing strict clears up the issue for me entirely: No error messages in the logs, NO problems with the script running, no indication of any trouble at all. Simply adding use strict; to that file shuts everything down to the point of one of these beauties:

Internal Server Error

The server encountered an internal error or misconfiguration and was u
+nable to complete your request.

Please contact the server administrator at webmaster@[redacted].com to
+ inform them of the time this error occurred, and the actions you per
+formed just before this error.

More information about this error may be available in the server error
+ log.
[download]

I haven't been able to verify that "strict" is giving only warnings. It is actually throwing a kill switch for me--and my script presently runs fine without it.