I just wanted to add that a client of mine had this very same error message and the issue was indeed opcache.
They had commented out its settings as a result of a similar, earlier issue with a redeclare warning, but opcache was still running. Turning it off completely and a server reboot has fixed the issue.