Disabling Resource Governor in SQL Server

Should I restart SQL Server after disabling the Resource Governor? What is the best practice?

Why am I asking this, because I am worried about existing open sessions in SQL Server. Will their behavior change (in terms of processor, memory and I / O) by default if we only disable the resource governor and do not restart SQL Services?

For example, if a particular session was limited to using 30% of the total system memory because of the resource governor. So, if we now disable the resource governor alone, will this one start using more than 30% instantly?