After reverting back to using the embedded Tomcat in CAS 5.0.4, this error still shows in the logs, so this seems to be an issue in CAS (pac4j) itself.
It seems to occur during ticket cleanup, such as after the TGT is destroyed for a user.
Has anyone else noticed this and is it something that we need to worry about, considering that the logout functionality seems to be working fine otherwise?