Like @KookieMonster, I fail to understand how a reboot can minimize or eliminate deadlocks, make CPU and memory message "cost efficient", minimize or eliminate memory leaks, or reduce resource consumption.
I have maintained plenty of SQL Servers that have uptimes of way longer than a year. @vonPryz makes a good point though, there are often very good reasons to reboot servers, most importantly service packs and other updates. You also need to restart SQL Server in the event of certain configuration changes - both to SQL Server and the underlying OS and/or hardware.
I did have one exception where we intentionally restarted one node in a cluster every week, but it was due to a bug in SQL Server 2005 (SP2 I think) where the "temp tables for destruction" counter just climbed and climbed exponentially and eventually choked the server (memory exhaustion). We were issued a private hotfix after about 6 months of this.
That is an edge case, though, and disappeared when we applied the hotfix (and was only ever seen on one cluster, even though several were configured identically and ran the same app). In almost all cases you should not be looking at restarting SQL Server as preventative maintenance. Focus on real problems you actually have, and troubleshoot those problems proactively instead of just assuming that a restart is a magic cure-all.
There's an old joke in IT: if your computer isn't working, reboot. Please don't treat SQL Server this way.