The good news is that the POODLE attack does not apply to IRC. It's not feasible.
Why? Two things: 1) It requires a high amount of reconnects, and 2) It requires chosen plaintext messages, in other words: the attacker must be able to choose what gets sent over the SSL/TLS connection.
This attack works for HTTP(S) because if the attacker controls the browser - like via javascript - he can make various GET requests, and at high speed too.
For IRC that's not the case. Chosen plaintext doesn't happen, the only case I could think of would be irc:// links from a browser but that will always prompt the user (plus.. how useful is that). And the high amount of reconnects is countered as well: all UnrealIRCd installations that use the default configuration file have throttling in place which limits you to 3 connections per second, that's really slow.
That being said, I think it's wise to add an option in a future version to control which SSL/TLS protocol is enabled. Similar to the cipher list. That way you can (more) easily disable the old SSL3 protocol.