I don't believe OO means everything is an object. Even in Object Oriented Analysis there are primitive attributes.
So what about static methods? Well since one of OO's intententions is to allow us to model the real world, the question is, does the real world containt something that a static method might emulate?
I'm willing to bet it does. Some operations in real life, at least to the point we want to capture them, are always the same even in seperate instances of these real world things. Also, some things are static and final right?
Maybe like a post-it. Presuming you want only so much precision each post-it has the same level of stickyness that could possibly be measured by a simple data type like a number... this number becomes static and final.
Basically I'm with William on this, except I like arguing a bit more

It's rediculous to think that it matters, or that anyone actually has a useful definition. The fact is, do you have a use for it? Is it necessary? Is is an embelishment?
If it's necessary, helpful, understandable or more or less useful then it doesn't really matter.
I personally have never seen a large application be successful and completely OO, so maybe even if it's not pure OO, that's a good thing.
------------------
David Roberts - SCJP2,MCP