OOP as described by java and C++ involves a graph of objects changing each others' state. This is not an orthogonal pattern to functional programming.

If you're thinking of functions operating on immutable objects and returning new objects then that is not typically what we refer to as a OOP pattern though technically it may fit the definition.

Java and C++ are just one way of doing OOP.

More universities should spend time teaching BETA, Self, CLOS, Smalltak, component based architectures.

I know. The dominant paradigm has changed the definition of the vernacular. Right now the default definition of OOP is the Java and C++ way unless you explicitly state otherwise.