IMO, I think it's fine for static based classes to reside in the /models dir. In working with Propel and Doctrine, they have Peer and Table classes (respectively), that are never meant to be instantiated, instead they are meant to implement business logic upon objects to which they are associated. Example dir listings:
// Propel
/lib/model/mydb
Vehicle.php // Instantiable
VehiclePeer.php // Works with vehicle object(s)
// Doctrine
/lib/model/mydb
Vehicle.php // Instantiable
VehicleTable.php // Works with vehicle object(s)
--Update--
Need to make a correction (doesn't change the answer), with respect to doctrine, the "*Table" classes CAN be instantiated, but they still behave the same as I described above, in that the included methods are meant to work with associated object(s). Your usage of the "static" classes is closer to the way Propel works, and as I mentioned earlier, acceptable to reside in the /model dir.
Adec_Model_Chat.