Meterpreter never touches the disk. So until you don't do anything deliberately that changes resources on the hard drive and leave evidence, chances are there will be no evidence on the disk. However, this is not so simple. OS can transfer pages from memory to disk when the system is low on memory. Although meterpreter reflective loader code specifically requests the OS not to flush the page to the disk where the meterpreter process is hosted, it's only a process request which can be ignored by the OS.
I am not going to explain the network part since it is out of scope here but a lot of times evidence is gathered from the network logs as well. SSL won't provide any benefit if it is intercepted in the middle (you have the option of certificate pinning in the stager code) but the bottom line is if you are concerned about forensics, make sure you are covered on all sides.