I wouldn't call that misuse, or even underuse. The key value Hudson brings to the picture is to reduce the cost of automation. Even if it's just doing things that you could otherwise do with a cron(8) job, it's still a valid use. Consider the appendix B in the book. This advocates using a personal Hudson instance to automate things such as workspace maintenance on an individual contributor's workstation.
Now, regarding the separate and more interesting question of how easy it is to configure and maintain Oracle's software, that's a product level concern. In my day-job, I work on GlassFish, and I must say that while it's easier to configure than WebLogic, there are still some challenges. What Hudson tries to bring to the picture is to make it possible to get useful things done, even when the other tools in the toolchain are not so well suited to automation.
subject: Hudson Continuous Integration in Practice: misuse